Is the job to get things done or to memorize trivia and solve cute coding puzzles?

Making small changes in large unfamiliar codebases is the job. That's what engineers do all day.

Yes SQL is super flexible. That is its strenght and its weakness

A reader asked 'Wtf why does this work?'

Team dysfunction where everyone's a soloist? Try this fix: Force the team to work on ONE story at a time.

Agile is something you are, not something you do.

Cap your down-side and think like an investor. Look for key metrics that can shape your career growth.

Transitioning from Senior to Lead Engineer isn't just about technical prowess, but strategic thinking, soft skills, and going beyond your role. And remember, strong individual contributions matter!

Understanding the nuances of TypeScript: it adds static types to JavaScript, reducing bugs by checking code validity pre-run. But imagine if we had types at run-time too - validating inputs, enhancing error messages. A dream, but a nice one.

Regular writing is a secret superpower! Sharpens your thoughts, boosts your career, and helps you become an authority in your field. Don't pretend to be an expert, just share your experiences. Your insights are gold

Why are utility files bad? How do you recognize architectural complexity? What the hell is a transitive dependency?

A few readers wrote in to say that the React Can Update State During Render email last week made no sense. Here's a better explanation.

Delete code when it stops providing value 💡 All code is a liability; context matters. Keep what solves problems, toss the rest.

Unlock the secret to guiding your career with a powerful positioning statement. Learn to stand out in the job market and attract opportunities that align with your expertise and values.

Don't worry about the hype, just get some sun, some rest, and remember to hydrate.

Don't overthink, just ship

Swiz shares why he's not making the big bucks at a tech giant, from the soul-crushing grind of corporate to the funny money of tech compensation.

Learn why squash merging is your friend - from hating it to loving it! Squash merging helps you keep moving and focus on the work instead of recording the work.

For those wanting to stay hands-on, we recommend solving bigger better challenges with higher stakes and new problems.

Here's an idea that can take the pressure off your career: Yes, you can stay a senior software engineer forever. But how?

Following up from my article about XState and Stately.ai, fellow reader S. asked if `useReducer` could ever be relevant when using state machines in React code. Yes! Here's how

Fellow reader Frank writes in with a question about career moves and I thought my answer could help you too

Great question. Common concern. *What if I get stuck in a technology that isn't hot??* Or worse, burn out re-learning every new thing 😱

New members on our team invariably say 2 things: 1. Wow I've never seen a team move this fast 2. This approach feels weird. I'm uncomfortable Teams like this are not common.

If your approach works so well, why isn't every team doing this?

Keep getting the guilt, that I'm not able to code, just running around for discussions and solving other issues, managing people. Any idea to manage all the fronts and get rid of this guilt?

Long time reader Phil asks when do you fix the tech debt you used to ship faster. Heroic efforts don't work. The real answer is "always" – a mindset of gardening.